Power management on an electronic device

ABSTRACT

In some examples, an electronic device may determine a target time to which the remaining battery charge is to last, such as based on a user input or historical usage of the electronic device. Additionally, the electronic device may determine a current amount of the battery charge remaining, and may determine user activities likely to occur between the present time and the target time. Based at least partially on the amount of the battery charge remaining and the user activities determined to be likely to occur before the target time, the electronic device may apply one or more power management restrictions to one or more resources of the electronic device.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional PatentApplication No. 62/353,310, to Michael A. Chan et al, filed Jun. 22,2016, which is incorporated herein by reference in its entirety.

BACKGROUND

People use electronic devices for communication, socializing,entertainment, work, navigation, web browsing, and a variety of otherfunctions. However, an electronic device typically has a limited amountof energy charged in the battery, thus restricting how often and for howlong a user may use the electronic device. For example, people may usetheir electronic devices throughout the day, and then may have to turnoff or otherwise limit the use of their devices toward the end of theday when they notice that their battery charges are close to beingdepleted. Additionally, some people may carry chargers and may attemptto find open electrical outlets to charge their electronic devices whentheir battery charges are running low. Furthermore, different peopleoften use their electronic devices in very different ways from otherpeople such that conventional power management configurations may not beuseful for some individuals.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 illustrates an example system for power management on anelectronic device according to some implementations.

FIG. 2 illustrates an example graphic user interface according to someimplementations.

FIG. 3 illustrates an example graphic user interface according to someimplementations.

FIG. 4 illustrates an example usage log data structure according to someimplementations.

FIG. 5 is a flow diagram illustrating an example process for powermanagement on an electronic device according to some implementations.

FIG. 6 illustrates select components of an example electronic deviceaccording to some implementations.

FIG. 7 illustrates select components of one or more example servicecomputing devices according to some implementations.

DETAILED DESCRIPTION

Some examples herein are directed to power management on an electronicdevice. For example, a power management service on the electronic devicemay monitor usage of the electronic device by the user of the electronicdevice and may implement one or more power management techniquesautomatically based on the remaining battery charge and predicted usage.In some cases, the power management settings may be dynamically adjustedin view of the predicted usage of the electronic device for extendingthe time until the battery charge is depleted to meet or exceed a targettime. As one example, the electronic device may determine the predictedusage of the electronic device based on past usage for the same day ofthe week, time of day, determined current location, etc., and mayperform power management to manage the remaining battery charge toenable use of the electronic device for the activities predicted to beperformed up through the target time.

In some examples, the power management may be incremented based on aplurality of different power management stages. As an example, there maybe a stage with no power management, and three power management stages,e.g., a first power management stage that minimally impacts the userexperience, a second power management stage that has a noticeable impacton the user experience, and a third power management stage thatsignificantly impacts the user experience. Of course, more or fewerpower management stages may be applied. For instance, each powermanagement stage may be progressively more aggressive in limiting thefeatures of the electronic device for increasing the power saved. Insome cases, there may be a hierarchy of power management features suchthat the successive stages progress further through the hierarchy tomore restrictive use of power. Additionally, the user may selectively orentirely override some or all of the power management features, asdesired. In the case that the user overrides power management features,the device may warn the user that the battery may be depleted before thetarget time is reached.

Further, in some examples, the user may manually set the target timeuntil which the user would like the battery to last. In response, theelectronic device may dynamically select an appropriate power managementstage to enforce based on predicted user activity that is likely tooccur up through the target time. The electronic device may determinethe current predicted battery charge level and may predict the futureusage of the electronic device until the target time. For instance, theelectronic device may determine the current usage (e.g., activitiescurrently being performed), recent usage (e.g., activities alreadyperformed today), historical usage, current day, current time, currentlocation, and so forth. Based on this, the electronic device may predicthow the battery charge will be depleted up until the target time and, ifnecessary to ensure that the battery charge lasts until the target time,may select a power management stage based on the predicted use of theelectronic device until the target time.

As the target time approaches, the electronic device may change theselected power management stage, such as moving up or down a stage, toensure that the remaining battery charge is sufficient for the predictedactivities that may occur until the target time is reached, but also toensure that the power management settings are not unnecessarilyrestrictive. Further, in some cases, rather than having the usermanually set the target time, the electronic device may predict thetarget time to which the user may desire the battery charge to last,such as based on past usage patterns, and may perform theabove-described functions in the same manner as if the user had manuallyselected the target time.

As mentioned above, the electronic device may determine when toimplement particular stages and/or may determine which of the powermanagement techniques to include in each stage based on past usage ofthe electronic device, such as for the same time of day and day of theweek. Accordingly, the electronic device may predict one or moreactivities that the user is likely to perform later, such as that theuser is likely to use a particular application to obtain a ride home,make a phone call at a particular time, respond to emails around acertain time, check a social media application a predicted number oftimes, read a news feed, and so forth. In addition, the electronicdevice may use other information when predicting upcoming user activity,such as by referring to the user's calendar to determine any scheduledevents. The electronic device may meter or otherwise control the use ofthe remaining battery power based on the predicted activities between acurrent time and the target time. Furthermore, if the user performs anactivity that is unexpected or does not perform an activity that isexpected, the electronic device may dynamically adapt the powermanagement settings based on this.

In some examples, machine learning may be used to determine and/or applythe power management stages. The machine learning may further be appliedto determine and apply one or more power management profiles that arecustomized for the user of the electronic device and for applicationsand/or categories of applications on the electronic device. For example,a neural network, statistical model, or other computational model may beused to determine and apply appropriate power management for particularsituations. As one example, the electronic device may maintain a usagelog that includes usage information about the applications and otherfeatures of the electronic device used by the user. For instance, theusage log may include the name of the application or feature used, thetime of day of the usage, the length of the usage, the day of the weekof the usage, the geographic location at which the usage occurred, andso forth.

The usage log information may be used as training data for thecomputational model. As one example, the usage log information may besent over a network to a service computing device, which may train aneural network, statistical model, or other type of computational model,and may provide the trained computational model to the electronic devicefor use in determining appropriate power management settings for aparticular time of day, day of the week, determined device location, andso forth. Alternatively, the electronic device itself may train andgenerate the computational model, such as at night while the electronicdevice is charging, or the like.

In some implementations, as part of implementing the power managementstages discussed above, one or more profiles may be used forimplementing different power-saving techniques for differentapplications on the electronic device. As an example, a plurality ofgeneric or otherwise default profiles may be established for differentcategories of applications. For instance, a first default profile may beimplemented for gaming applications, a second default profile may beimplemented for social media and messaging applications, a third defaultprofile may be implemented for navigation and mapping applications, afourth default profile may be implemented for media playbackapplications, a fifth default profile may be implemented for webbrowsing applications, and so forth. Each default profile may be furthercustomized for individual applications, such as based on informationdetermined about the individual application from observed usage, userinputs, and/or from metadata associated with the application.

The profiles may enable the power management to be incremented in ahierarchical manner based on the usage of the electronic device, theremaining battery charge amount, and the predicted usage through to atarget time, while also allowing use of applications and other functionsof the electronic device. For instance, when applying power management,the electronic device may reduce the screen refresh rate and the numberof frames per second (FPS) rendered for particular applications and/orgraphic user interfaces (GUIs) to effect a reduction in powerconsumption. To progressively increase power savings, such as whenadvancing power management from the first stage to the second stage orthird stage, the FPS may be progressively reduced for some applicationsand GUIs. Further, the electronic device may perform a number ofadditional power saving techniques, such as reducing the display refreshrate; throttling the CPU(s), GPU(s), or other processors, limiting turbomode or otherwise limiting the clock speed on some processing cores,reducing display brightness, reducing frequency of certain operations orprocesses, reducing network communication, turning off certain features,and so forth.

As one example, a default profile for applications classified in agaming category may reduce the frame generation rate in software, suchas by reducing the number of frames rendered from 60 frames per second(FPS) to e.g., 45, 40, 30 FPS, and so forth, depending on the type ofgame. In addition, the display hardware may also be controlled, such asto reduce the display refresh rate to be equal to or greater than theframe generation rate, and/or to reduce the display brightness. Otherpower reduction actions for gaming category applications may includethrottling one or more processors or processor cores, reducing thefrequency of network communications, and the like.

As another example, a default power management profile for applicationsin a mapping or other navigation category may reduce the frequency ofthe usage of the GPS (Global Positioning System) receiver, may reducethe frames per second rendered, may reduce the display refresh rate, mayreduce display brightness, may reduce the frequency of communicationwith a server over a network, and so forth. Accordingly, each respectivedefault power management profile may be configured for a respectiveapplication category such that power savings may be achieved initiallywithout substantially affecting the user experience (e.g., powermanagement stage one).

The power management profiles may be further configured to advance thepower management from stage one to stage two and/or stage three by moreaggressively restricting certain features or employing other powersaving techniques. For instance, as the first stage of power management,a default power management profile for the gaming category may initiallyreduce the FPS rendered from 60 to 45 FPS and may reduce the displayrefresh rate from 60 Hz to 45 Hz. Subsequently, as the second stage ofpower management, the default gaming profile may reduce the displayrefresh rate to 45 Hz, may implement processor throttling, e.g., asdiscussed additionally below, and may reduce network communications.Further, during the third stage of power management, if the user desiresto continue playing a game, the default gaming profile may reducedisplay brightness, may reduce the frames rendered from 45 to 30 FPS,may reduce the display refresh rate to 30 Hz, may further throttle theprocessors, may eliminate network communications, and so forth.

Further, in some examples, a service provider may provide optimizedpower management profiles that are optimized for popular applicationsfor particular models of electronic devices. In some cases, the serviceprovider may update these optimized power management profiles as theapplications themselves are updated. Additionally, the user may be ableto adjust the settings for a particular profile, and may be able to savethe settings as a custom profile either for a particular application orfor a particular application category.

In some examples, the power management service may be an application,program, or other executable module that is part of the OS. In otherexamples, the power management service may be an application, program,or other executable module that is separate from the OS. In eitherevent, the power management service may include or may resemble anapplication that the user may be able to see and access via a graphicuser interface (GUI), such as for adjusting settings of the powermanagement service in general, adjusting settings of particular powermanagement profiles, setting target times, and so forth. Alternatively,in other examples, the power management service may be implemented as amodule of the OS that is not accessible to the user. As still anotheralternative, the power management service may be an application separatefrom the OS that the user cannot see.

In some examples, the power management service on the electronic devicemay use one or more APIs to communicate over a network with a servicecomputing device executing a service module. For instance, the servicemodule may include one or more programs or other executable codeconfigured to train a computational model based on gathered usageinformation about the user. The electronic device may use the API(s) tosend, to the service computing device, the usage information includingusage log data about how and where the user uses the electronic device,which applications and features the user uses, when the user uses theapplications and features, and so forth. Based on the received usageinformation, the service computing device may train a computationalmodel and may send the computational model to the electronic device tobe used for predicting future usage of the electronic device, predictinga target time to which the user would like battery to last, determiningwhen to implement power management, which power management stages and/orapplication profiles to implement, and so forth.

For discussion purposes, some example implementations of a powermanagement service are described in the environment of a mobileelectronic device for conserving a battery charge on the electronicdevice with minimal disruption to the user experience. However,implementations herein are not limited to the particular examplesprovided, and may be extended to other types of devices, other executionenvironments, other system architectures, other power conservationtechniques, and so forth, as will be apparent to those of skill in theart in light of the disclosure herein.

FIG. 1 illustrates an example system 100 for enabling power managementaccording to some implementations. For instance, the system 100 mayenable an electronic device 102 associated with a user 104 tocommunicate over one or more networks 106 with one or more servicecomputing devices 108 of a service provider. The electronic device 102may be a type of portable or otherwise mobile computing device that usesa battery 110. Some examples of the electronic device 102 may includecellular phones, smart phones, tablet computing devices, wearablecomputing devices, body-mounted computing devices, and other types ofmobile devices; laptops, netbooks, and other mobile computers orsemi-mobile computers; augmented reality devices, gaming systems, or anyof various other computing devices capable of storing data, sendingcommunications, and performing the functions according to the techniquesdescribed herein. Further, while a single user 104 and associatedelectronic device 102 are illustrated in this example, in otherexamples, there may be a large number of users 104, each having one ormore respective electronic devices 102.

The electronic device 102 may include an operating system 112 thatincludes a power management service 114 that executes on the electronicdevice 102. The power management service 114 may include executable codeor other executable instructions that provide power managementfunctionality to the electronic device 102 for controlling features andresources of the electronic device 102 for effecting power management.In some examples, the power management service 114 may be one or moremodules of the operating system (OS) 112 on the electronic device 102.In other examples, the power management service 114 may be one or moremodules that are separate from the OS 112, such as may be included in aseparate application, which may be one of a plurality of applications116 executable on the electronic device 102. Further, whether as an OSmodule or as a separate application, the power management service 114may have permission for system-level access to the applications 116 thatare executable on the electronic device 102, as well as to variousdrivers, such as a display driver, a GPU driver, and other OS modules117. In addition, while the power management service 114 is illustratedin this example as residing on the electronic device 102, in otherexamples, at least some of the functionality of the power managementservice 114 may reside on another suitable computing device. Inaddition, as mentioned above, the OS 112 may include a number of otherOS modules 117, such as drivers and other executable modules forcontrolling various functions and aspects of the electronic device 102.

The electronic device 102 may further include, for the applications 116,associated application data 118, and application metadata 120. Theapplications (apps) 116 may be installed and executable on theelectronic device 102. The application data 118 may include userapplication data that is associated with, generated by, and/or used byrespective applications 116. For instance, each application 116 may havean associated portion of application data 118, respectively. Inaddition, the application metadata 120 may include information about theapplications 116, such as the name of the application, a source of theapplication, an application category, a storage size, and so forth. Inaddition, the electronic device 102 may store one or more content items122. Examples of content items 122 may include digital photographs orother images, videos, audio recordings, documents, books, movies,television shows, and the like.

In addition, the electronic device 102 may maintain a usage log 124,which may include a record of each time the user 104 uses the electronicdevice 102, such as causing execution of an application 116 on theelectronic device. Furthermore, the usage log 124 may include a recordof each time the user accesses the electronic device 102, such as tocheck messages or notifications, make a telephone call, send a message,use the camera, interact with the operating system, or perform otheruser activities which may be referred to herein as using one or morefeatures of the electronic device 102. Accordingly, the usage log 124may include a record of each time the user uses an application or otherfeature of the electronic device 102, including the day and time onwhich the application or feature was used, the length of time for whichthe application or feature was used, the geographic location of theelectronic device when the application or feature was used, and possiblyother information such as a starting battery level and a finishingbattery level during use of the application or feature, locations of thedevice before and/or after the application or feature was used, or thelike.

In some cases, the electronic device 102 may include a computationalmodel 126 that may include settings or other information for themultiple power management stages discussed above, and the electronicdevice 102 may also include a plurality of power management profiles 128that may be applied based on corresponding application or featuresselected by the user. A display 130 may be associated with theelectronic device 102 for presenting various types of visual informationto the user 104, such graphic user interfaces (GUIs) presented by theoperating system or the applications 116, as well as other UIs, contentitems, text, images, or other digital information.

Additionally, in this example, the electronic device includes a GPSreceiver 132 that may be used for determining at least partially ageographic location of the electronic device 102. Further, while severalexecutable programs or modules, hardware components, and data of theelectronic device 102 are described and illustrated in this example,numerous other types of programs, system data, user data, user settings,user account information, hardware components, and so forth, may beincluded in the electronic device 102, as discussed additionally hereinand/or as will be apparent to those of skill in the art having thebenefit of the disclosure herein.

In the illustrated example, the one or more service computing devices108 may include a service module 138 that is executable to send andreceive communications with the electronic device 102. Further, theservice computing device 108 may include, or may be in communicationwith, one or more storage devices 140, such as by direct connection orvia the one or more networks 106. In the case that the service computingdevice 108 provides a commercial storage service, the storage devices140 may be enterprise level storage arrays, such as may be maintained ina storage area network, a NAS cluster, a RAID (redundant array ofindependent disks) array, a distributed storage node array, or variousother types of storage configurations.

The one or more networks 106 may include any suitable network, includinga wide area network, such as the Internet; a local area network, such asan intranet; a wireless network, such as a cellular network; a localwireless network, such as Wi-Fi; short-range wireless communications,such as BLUETOOTH®; a wired network, such as fiber or Ethernet; or anyother suitable network, or any combination thereof. Accordingly, the oneor more networks 106 may include both wired and/or wirelesscommunication technologies. Components used for such communicationtechnologies can depend at least in part upon the type of network and/orthe environment selected. Protocols for communicating over such networksare well known and will not be discussed herein in detail. Accordingly,the electronic device 102 and the service computing device 108 are ableto communicate over the one or more networks 106 using wired or wirelessconnections, and combinations thereof.

The service module 138 on the service computing device 108 may receivethe usage information 142 from the power management service 114, such asvia one or more APIs, or the like. For example, the power managementservice 114 may send usage information 142 including informationobtained from the usage log 124 to the service computing device 108 toenable the service computing device 108 to train the computational model126. Accordingly, the service module 138 may incorporate the usageinformation 142 into training data 146. The training data 146 mayinclude the usage information 142 about the user 104, and in someexamples, may include aggregated usage information from other usershaving the same or similar electronic devices 102.

Further, the service module 138 may train a different computationalmodel 126 for each separate user 104 and/or each separate electronicdevice 102 of a plurality of users 104 associated with a plurality ofrespective electronic devices 102. For instance, each computationalmodel 126 may be trained for a particular user 104 and a particularelectronic device 102 based at least partially on the respective usageinformation 142 received from that particular electronic device 102.

In some implementations, the power management service 114 maydynamically manage the amount of the battery charge remaining on theelectronic device 102. In some cases, the power management service 114may use the computational model 126 for determining when to implementpower management, while in other cases, the power management service 114may determine usage patterns directly from the usage log 124, withoutuse of the computational model 126.

In the case that that usage patterns are determined directly from theusage log 124, the power management service 114 may observe applicationusage and other device feature usage by the user 104 to determine usagepatterns for the user 104 with respect to particular applications 116and other device features, and may store this information in the usagelog 124. For instance, the power management service 114 may determinethat the user typically begins charging the electronic device 102 atnight between 11:00 PM and 11:30 PM on weekdays and between midnight and1:30 AM on Fridays and Saturdays. Based on this, the power managementservice 114 may establish a target time for the battery charge to lastto be 11:30 PM on weekdays and 1:30 AM on Fridays and Saturdays.Furthermore, based on the observed usage of applications 116 and otherdevice features on individual days of the week, the power managementservice 114 may establish patterns of use of applications and devicefeatures for each day of the week, and may use this information whendetermining whether power management is necessary for individual days ofthe week, and for predicting what applications and features will be usedby the user 104 on each day of the week.

Thus, the power management service 114 may determine usage patternsdirectly from the usage log 124 for determining when to implement powermanagement on the electronic device 124. The power management service114 may determine which applications 116 are likely to be used by theuser 104 in the near future, i.e., before the next time the user chargesthe battery 110 on the electronic device 102. The power managementservice 114 may employ one or more observed user usage patterns andexpressed user preferences when determining device resources andfeatures to limit for obtaining power savings.

Additionally, or alternatively, the power management service 114 may usethe computational model 126 for determining power management. Forexample, the power management service 114 may apply one or more inputsof current information to the computational model, such as a currenttime of day, day of the week, battery level, usage log informationalready recorded this day, current geolocation, and the like, whendetermining which power management stage to implement, when to implementa particular power management stage, and which power management profilesto apply and/or features and resources to restrict on the electronicdevice 102. For instance, the computational model 126 may be used tomake determinations and other types of predictions based on inputteddata. As one example, the computational model 126 may be a neuralnetwork or statistical model that includes a set of assumptionsconcerning data based in part on information about similar datadetermined from a larger population of data. For instance, thecomputational model may be configured with one or more mathematicalequations that relate one or more random variables and, in some cases,non-random variables. Typically, prior to being used to makepredictions, the computational model may be trained using a quantity oftraining data 146, which in this example may include at least usageinformation 142 from the usage log 124 of the user 104, and in someexamples, may also include usage information from other users, such asother users determined to have a similarity to the current user in oneor more demographic aspects.

Examples of suitable computational models 126 that may be used in someimplementations herein may include predictive models, decision trees,classifiers, regression models, such as linear regression models,support vector machines, and stochastic models, such as Markov modelsand hidden Markov models, artificial neural networks, such as recurrentneural networks, and so forth. Accordingly, after the computationalmodel 126 is been trained, the computational model 126 may be used bythe power management service 114 to provide predictions of useractivities and determinations of power management stages to apply basedon the current day, current time, current location, current remainingbattery charge, and/or activities already performed by the user duringthe current day.

As mentioned above, in some cases the computational model 126 may betrained by the service computing device 108 and provided to theelectronic device 102, while in other cases, the electronic device 102may train the computational model 126. In the case that the servicecomputing device 108 trains the computational model, the service module138 may receive the usage information 142 and may store the usageinformation 142 in association with a user account associated with theuser 104 and/or the electronic device 102. As one example, the user'susage information 142, computational model 126, training data 146, andother user data 148, such as backup data or the like, may be stored atthe network storage devices 140 in association with a cloud storageaccount of the user 104 of the electronic device 102. The service module138 may train the computational model 126 and may send the computationalmodel 126 to the electronic device 102 for use by the power managementservice 114 for determining when and how to apply power management.

Whether used for generating the computational model 126, or when usedwithout the computational model 126, the usage log 124 typically mayprovide a high level of confidence of a time at which the user 104 willcharge the electronic device 102. Further, the electronic device 102 maydetermine a current location and the location at which chargingtypically occurs, such as may be determined using the

GPS receiver 132. For example, supposed that on Tuesday nights, the usertypically begins charging the electronic device between 11:00 PM and11:30 PM. Further, suppose that the current time is 10:00 PM and user isat a location 10 miles from home, and that the user 104 typically uses aride sharing application around 10:30 PM when at the current location.Based on this information, the electronic device 102 may predict thatthe user 104 is likely to use the ride sharing application tonight, andmy implement a power saving stage that is likely to ensure that there isenough battery left at 10:30 PM to enable the user to use the ridesharing application and also perform any other activities that the usertypically performs between 10:00 PM and 11:30 PM, or that the userotherwise typically performs but has not yet performed tonight.

Alternatively, if the user is in a location that is not the usuallocation, e.g., 30 miles from home, the power management service 114 maychange the target time from 11:30 PM to a later time, may go to a higherpower management stage than usual, such as switching from stage 1 tostage 2, or the like. Thus, the power management service 114 maycorrelate the current location information and current usage informationwith the historical location information and historical usageinformation from the usage log 124 to attempt to predict future usage ofthe electronic device between a current time and the target time.

As another example, suppose that in one or more of the power managementstages, the electronic device 102 is configured to go into a sleep modeafter a certain amount of time in standby mode, such as 20 minutes.Further, suppose that, based on the user's calendar, the powermanagement service 114 determines that the user is scheduled to attend ameeting during the next hour. Accordingly, rather than waiting for thepredetermined amount of time in standby mode, the power managementservice 114 may cause the electronic device 102 to automatically enterthe sleep mode as soon as the meeting starts, or shortly thereafter,instead of waiting for 20 minutes.

As mentioned above, the power management service 114 may apply powermanagement settings according to several power management stages, suchas three power management stages in some examples herein. Furthermore,the power management service 114 may provide a popup window or othernotification to the user as each stage is entered. As severalnon-limiting examples, stage 1 may be configured to have minimal impacton the user experience, such as by throttling the CPU clock speed,reducing the frame rate/display refresh rate for some apps, and soforth. Stage 2 may begin to have a noticeable impact on the userexperience and may produce noticeable degraded performance for someapplications. Thus stage 2 may include the stage 1 restrictions, plusheavier CPU throttling, may include preventing core turbo modes fromengaging, may include dimming the display, reducing the frame rate andrefresh rate more for some applications, reducing background networkactivity and notifications, and so forth. Stage 3 may heavily impact theuser experience, and may include stage 2 restrictions, plus turning offbackground network activity and notifications, turning off vibrations,turning off animations in GUIs, turning off the display for certainuses, going into a sleep mode, or the like.

Additionally, in some examples, the different stages may be applied on aper application basis and per feature basis, rather than being applieduniformly across all activity on the electronic device 102. Thus, thepower management profiles 128 may be preconfigured for particularapplications and features on the electronic device 102 so that theimpact on usability of the applications and features due to the powermanagement is minimized For instance, the power management service 114may determine a power management profile 128 associated with eachapplication 116, and may determine which power management restrictionsto apply to each application based at least partially on the associatedprofile 128.

As one example, suppose that the user 104 frequently plays games on theelectronic device 102, and is willing to sacrifice some game performanceto be able to play the games twice as long without fully depleting thebattery 110. Thus, the power management service 114 may determine theappropriate restrictions to apply during power management stages 1, 2,and 3, for the power management profile 128 for one or more particulargame applications, such as based on a selected power management profile128 for the particular application, past user usage patterns, pastmanually input user settings for the particular application, or thelike.

Alternatively, suppose that the user does not want to have theperformance throttled when playing games, but is willing to sacrificeperformance of other applications and features of the electronic device102. Accordingly, the user may instruct the power management service 114to not apply any power saving techniques to game applications, butinstead, apply more stringent power management techniques to otherapplications and features on the electronic device 102. Thus, the gameapplication may be used as long as possible without restrictions, whileother applications and features may operate under power management stage3. Subsequently, if the power management service 114 determines that thebattery charge is predicted to be depleted before the target time, thepower management service 114 may notify the user of this situation, andthe user may decide whether to enter a power management stage for thegame application, e.g., stage 2, stop playing the game applicationaltogether, or continue playing and have the battery charge run outbefore the target time.

As mentioned above, when performing power management, in some examplesherein, the frame rendering rate may be reduced for some applications.For instance, the frame rate, i.e., the rendered frames per second foran application, may be reduced for many applications 116 withoutsignificantly affecting the user experience. The application 116 itselfmay be controlled in software to limit the number of frames rendered persecond, such as by controlling a GPU driver to limit the number offrames that are rendered per second to a desired FPS, e.g., 45, 40, 30FPS etc., depending on the category of application and/or the particularattributes of the particular application. For instance, the GPU drivermay be throttled by controlling the FPS rendered for a particularapplication being executed based on a predetermined setting forachieving a desired power savings while maintaining usability of theapplication.

The FPS for individual applications may be determined based on acategory of the individual application and/or based a profile determinedfor the individual application in advance, or a combination thereof. Asan example, the FPS for a social network application may besubstantially lower than the FPS for a first-person-shooter game. Insome cases, a large number of popular applications may have respectivepower management profiles 128 generated in advance of execution of therespective applications and stored on the electronic device 102. If anapplication 116 that is currently being executed on the electronicdevice 102 does not have a corresponding application-specific powermanagement profile 128, then a default power saving profile may beapplied to the application based on a category within which theparticular program is classified. As one example, the applicationmetadata 120 may indicate the application category for each application.

In addition, the refresh rate of the display 130 may be controlled forlimiting the number of times per second the display is refreshed. Forinstance, if the display 130 normally refreshes 60 times per second(i.e., 60 Hz), the refresh rate may be reduced to reduce that number oftimes per second that the display 130 is redrawn. In some examples, therefresh rate may be reduced to match the frame rendering rate of theapplication. For example, if the frame rendering rate of the applicationis limited to rendering 45 FPS, the refresh rate of the display may belimited to a display refresh rate of, e.g., 45 Hz, or in some cases arefresh rate greater than 45 Hz or less than 45 Hz. If the displayrefresh rate is limited to less than 45 Hz, however, then the FPSrendered may also be reduced to equal the display refresh rate so thatenergy is not wasted rendering frames that may not be displayed. Thekernel of the operating system 112 may include a setting for controllingthe refresh rate of the display, such as for changing a display driversetting for the display based on a detected application being executedfor presentation on the display. As one example, the kernel may controla clock setting that controls the refresh rate of the display, and theclock setting may be adjusted by the power management service 114 tocontrol the refresh rate of the display.

Further, in some examples, during enforcement of the power managementstages 1-3, such as by applying one or more of the power managementprofiles 128, the relative loads on the GPU and CPU may be monitored,and adjusted. For example, if an application is primarily using the GPU,the clock speed on the CPU may be reduced while that application isbeing used. For example, when throttling the CPU a voltage range may belimited to limit the frequency at which the CPU is able to operate.Further, a turbo mode (high frequency clock speeds) on some cores may bedisabled, so that the maximum frequency of these cores is limited to aset maximum frequency. As one example, suppose that in turbo mode, aprocessor core may be able to operate at 1.44 GHz, but if the turbo modeis disabled, the core may only be able to operate at 787 MHz. As aresult, when the load on this core is causing the core to operate at amaximum frequency (e.g., 787 MHz), some of this load may beautomatically transferred to other cores, which may have unusedcapacity, thus balancing the load among the cores while saving power dueto the lower clock speeds being enforced on the cores. For example, manyapplications and other tasks do not require high-frequency processing.

When determining the power management profile 128 for a particularapplication, the power management service 114 may determine the type ofapplication from application metadata 120 in some examples.Alternatively, the electronic device 102 may initially run theapplication 116 for a threshold time, e.g., 30 seconds to one or twominutes, and may monitor the GPU usage, CPU usage, frame rendering rate,GPS usage, network communications, and so forth. Based on the collectedinformation, the power management service 114 may categorized theapplication in one of the default power management profiles 128.Subsequently, the next time the application 116 is used, the powermanagement service 114 may automatically apply the selected defaultpower management profile 128 as applicable.

Further, the user 104 may change the default power management profile128 applied to a particular application 116, may change some of thepower management settings of the power management profile 128 for aparticular application 116, and so forth. In addition, certain popularapplications may have application-specific power management profiles 128that may be optimized for those particular applications, and which maybe applied automatically when those particular applications areexecuted, such as based on application metadata 120. These designatedpower management profiles 128 may be updated periodically by the servicemodule 138, such as based on updates to the respective applications, toensure that the power management profiles 128 remain optimized for theparticular application and for the hardware of the particular electronicdevice 102.

FIG. 2 illustrates an enlarged example view of the electronic device 102with an example GUI 202 presented on the display 130 according to someimplementations. In this example, suppose that the power managementservice 114 has determined that power management may be used to helpextend the battery charge to a target time. Accordingly, the electronicdevice 102 may present a pop-up window or other GUI 204 including anotification 206 to inform the user that the electronic device 102 isentering one of the stages of power management. For instance, in thisexample, suppose that the electronic device 102 is entering the stage 1power management mode, as discussed above.

Furthermore, in this example, the pop-up window 204 may include thetarget time 208 for battery management, which in this example is 11:15PM. In some cases, as discussed above, the power management service maypredict the target time automatically based on the usage log informationand/or the computational model. Additionally, the GUI 204 may include abutton or other virtual control 210, that the user may select to changethe predicted target time to a different target time, such as dependingon the user's current plan for when the electronic device 102 will nextbe charged.

In addition, in this example, the pop-up window 204 includes a listing212 of the predicted user activities that are predicted to take placebetween a current time and the target time 208. As one example, the usermay be able to scroll through the predicted activities 212 to view theactivities that the power management service is predicting the user willperform. Furthermore, the GUI 202 may include a button or other virtualcontrol 214 that the user may select to add, delete, or otherwise changethe predicted activities 212. For instance, the user may add one or moreactivities such as from a menu that is presented if the user selects thevirtual control 214.

Additionally, if the user does not want to enter the power managementmode, the user may select a reject button 216. On the other hand, if theuser agrees to enter the power management mode, the user may select anokay button 218. In some implementations, one or more additional GUIs(not shown in FIG. 2) may enable the user to interact with theelectronic device 102 for controlling additional power managementfeatures on the electronic device 102, such as for setting up particularapplication profiles, default profiles, or the like. Furthermore, insome examples, the electronic device 102 may include variousinput/output (I/O) components, such as speakers 220, a camera 222, and aproximity sensor 224.

FIG. 3 is an example GUI 302 according to some implementations. In thisexample, suppose that the GUI 302 includes a plurality of applicationicons 304. Further, suppose that the user has selected an applicationicon 304(1) from among the plurality of application icons 304. Inresponse, suppose that the power management service provides a pop-upwindow 306 indicating that the stage 1 power management mode is ineffect, and asking whether the user would like to run the selectedapplication in the power management mode, as indicated at 308.Furthermore, the pop-up window may indicate the details of the powermanagement mode that will be implemented such as based on acorresponding power management profile for the selected application304(1).

In this example, as indicated at 310, suppose the power managementprofile for the selected application indicates that the frame renderingrate will be reduced from 60 to 45 FPS; as indicated at 312, the screenrefresh rate will be reduced; and as indicated at 314, the screenbrightness will be reduced. The user may scroll to view additional powermanagement options that will be implemented.

Furthermore, the user may have the opportunity to deselect one or moreof the power management options that will be implemented, such as bytapping on a particular deselection icon 316, 318, and/or 320,respectively. If the user would like to proceed with the power savingmode, the user may select a button or other virtual control 322. If theuser would not like to proceed with the power saving mode, the user mayselect a button or other virtual control 324. If the user would like tochange the power settings, the user may select a button or other virtualcontrol 326 to be presented with an additional GUI for managing thepower management settings.

FIG. 4 illustrates an example data structure of the usage log 124according to some implementations. In this example, the usage log 124includes a time 402 at which the user started using a particularapplication or feature of the electronic device. Further, the usage log124 includes an identifier 404 of the application or feature; a durationof use 406; a starting battery level 408, e.g., in percent; an endingbattery level 410; a geolocation 412 at which the activity wasperformed; a power management mode 414 that was in effect when theactivity was performed; and a power management profile 416 that wasapplied during the usage of the application or feature.

In this example, two example entries in the usage log 124 areillustrated; although, typically there may be a large number of entries.For instance, an entry may be made every time the user, accesses theelectronic device, opens an application, and/or uses a feature of theelectronic device. A first example entry 418 indicates that the userused a social media application on the electronic device for 15 minutesand 11 seconds while the electronic device was in the stage 1 powermanagement mode and while the electronic device was restricting somecomputing resources of the electronic device by applying anapplication-specific profile for the application. Further, during theusage of the social media application, the battery level fell from 77percent to 75 percent. Next, as indicated by a second example entry 420,the user made a telephone call that lasted 1 minute and 46 seconds.During the call, the battery level fell from 75 percent to 74 percent,and the power management profile applied during the call was the defaultpower management profile for the telephone feature.

Through the usage log, the amount of battery charge used by variousapplications and features in various power management modes may bedetermined and may be used for predicting how much battery charge mightbe needed for activities that are predicted to be performed later in theday until the target time is reached. Further, while several selectedmetrics are illustrated as being recorded in the usage log 124 in thisexample, fewer, more, or different metrics may be recorded in the usagelog 124 in other examples.

FIG. 5 is a flow diagram illustrating an example process according tosome implementations. The process is illustrated as a collection ofblocks in logical a flow diagram, which represents a sequence ofoperations, some or all of which can be implemented in hardware,software or a combination thereof. In the context of software, theblocks may represent computer-executable instructions stored on one ormore computer-readable media that, when executed by one or moreprocessors, program the processors to perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures and the like that performparticular functions or implement particular data types. The order inwhich the blocks are described should not be construed as a limitation.Any number of the described blocks can be combined in any order and/orin parallel to implement the process, or alternative processes, and notall of the blocks need be executed. For discussion purposes, the processis described with reference to the environments, architectures, devices,and systems described in the examples herein, although the process maybe implemented in a wide variety of other environments, architectures,devices, and systems.

FIG. 5 illustrates an example process 500 for power management accordingto some implementations. In some examples, the process 500 may beexecuted by the electronic device 102 or by another suitable computingdevice.

At 502, the electronic device may record applications and/or featuresused in usage log, along with time of usage, starting battery chargeamount and ending battery charge amount, power management stage andpower management profile in effect at the time, a geographic location ofthe usage, a duration of the usage, and the like. In some examples, theelectronic device may send, to a computing device over a network, atleast a portion of information included in the usage log, and inresponse, may receive, from the computing device, a computational modelgenerated based at least partially on the portion of information sentover the network. For instance, the computational model may be used fordetermining various information, such as a target time, user activitiespredicted to occur before the target time, and/or a recommended powermanagement stage.

At 504, the electronic device may determine a target time to which abattery charge is to last, such as until the next time the battery isexpected to be charged. As one example, the user may manually enter thetarget time. Alternatively, the electronic device may determine thetarget time based on historical usage data obtained from the usage logand/or by applying one or more inputs to a computational model. Forinstance, the target time may be predicted by the electronic devicebased on a current location and recent locations of the electronicdevice (e.g., geolocations already visited that day), and further basedon the time at which the electronic device has usually been charged inthe past when the electronic device has been at those locations, such ason a same day of the week, such as when the electronic device has beenused to perform similar activities, and so forth.

At 506, the electronic device may determine a current amount of thebattery charge remaining, such as a percentage or other amount ofbattery charge remaining. As one example, the OS may have a module foraccessing a power controller associated with the battery that maydetermine the amount of battery charge currently held by the batterysuch as a percentage of total charge, a charge level in milliamp hours(mAh), or the like.

At 508, the electronic device may determine one or more user activitieslikely to occur between a present time and the target time. For example,based at least partially on the historical usage data in the usage log,the electronic device may determine one or more user activities that theuser is likely to perform during the current day from the current timeuntil the target time. For example, based at least partially on currentand recent geolocations and/or for a particular day of the week, theelectronic device may determine the applications and features on theelectronic device that are likely to be used between the present timeand the target time. These applications and features predicted to beused may be listed as predicted user activities. In some examples, thepredicted user activities may be determined by using a computationalmodel trained, at least in part, using the historic usage loginformation.

At 510, the electronic device may determine how much of the batterycharge is predicted to be depleted between the current time and thetarget time based on the predicted user activities. For example, theelectronic device may maintain in the usage log the amount of batterycharge used by each activity in the past. Further, in some cases theusage log may indicate how much batter charge is used by each activityin different power management modes, such as under normal mode, stage 1power management mode, stage 2 power management mode, and/or stage 3power management mode. Accordingly, based on the history of batterycharge depletion included in the usage log information, the electronicdevice is able to determine which power management stage to employ forthe user activities that are currently predicted to take place beforethe target time is reached.

At 512, based on the amount of the battery charge remaining, thedetermined user activities likely to occur before the target time,and/or the amount of the battery charge predicted to be depleted, theelectronic device may apply one or more power management restrictions toone or more resources of the electronic device. As one example, thepower management restrictions may include restricting a number of framesper second rendered for presentation on the display and/or restricting arefresh rate of the display. Numerous other examples of power managementrestrictions are discussed above. Additionally, the one or more powermanagement restrictions may be applied according to a plurality ofstages, e.g., a first stage may include less restrictive powermanagement restrictions and a second stage may include more restrictivepower management restrictions, and so forth. One of the stages may beselected based at least partially on the determined user activitieslikely to occur before the target time.

In addition, a plurality of application-specific power managementprofiles and/or default application category power management profilesmay be stored in the computer-readable media. Each application-specificpower management profile may indicate the one or more power managementrestrictions to apply to the one or more resources for an individualapplication of a plurality of applications installed on the electronicdevice. Further, each application category power management profile mayindicate the one or more power management restrictions to apply to theone or more resources for a category of application installed on theelectronic device.

Furthermore, as additional applications and/or features of theelectronic device are used by the user, the electronic device may repeatthe process of blocks 502-512 so that the power management settings ofthe electronic device may be continually updated based on the latestusage information and the current battery charge amount remaining.

The example processes described herein are only examples of processesprovided for discussion purposes. Numerous other variations will beapparent to those of skill in the art in light of the disclosure herein.Further, while the disclosure herein sets forth several examples ofsuitable frameworks, architectures and environments for executing theprocesses, implementations herein are not limited to the particularexamples shown and discussed. Furthermore, this disclosure providesvarious example implementations, as described and as illustrated in thedrawings. However, this disclosure is not limited to the implementationsdescribed and illustrated herein, but can extend to otherimplementations, as would be known or as would become known to thoseskilled in the art.

FIG. 6 illustrates select example components of the electronic device102 that may implement the functionality described above according tosome examples.

The electronic device 102 may be any of a number of different types ofcomputing devices, as enumerated above. In the example of FIG. 6, theelectronic device 102 includes a plurality of components, such as atleast one processor 602, one or more computer-readable media 604, one ormore communication interfaces 606, and one or more input/output (I/O)devices 608.

Each processor 602 may itself comprise one or more processors orprocessing cores. For example, the processor 602 can be implemented asone or more microprocessors, microcomputers, microcontrollers, digitalsignal processors, central processing units, state machines, logiccircuitries, and/or any devices that manipulate signals based onoperational instructions. In some cases, the processor 602 may be one ormore hardware processors and/or logic circuits of any suitable typespecifically programmed or configured to execute the algorithms andprocesses described herein. The processor 602 can be configured to fetchand execute computer-readable processor-executable instructions storedin the computer-readable media 604. In this example, the processorincludes one or more faster cores 612 and one or more slower cores 614.For instance, in some examples, the processors 602 may include one ormore CPUs with a BIG.LITTLE® architecture or other heterogeneouscomputing architecture that includes a mix of faster cores 612 andslower cores 614. For instance, a CPU may include four faster cores 612and four slower cores 614. Further, in some examples, the maximumfrequency of the cores may be throttled, or otherwise limited to limitthe power consumption of the processors. In addition, the processors 602may include one or more graphic processing units (GPUs) 616, which mayalso be controlled, such as for controlling a frame rendering rateand/or for controlling an operating frequency.

Depending on the configuration of the electronic device 102, thecomputer-readable media 604 may be an example of tangible non-transitorycomputer storage media and may include volatile and nonvolatile memoryand/or removable and non-removable media implemented in any type oftechnology for storage of information such as computer-readableinstructions, data structures, program modules, or other data. Thecomputer-readable media 604 may include, but is not limited to, RAM,ROM, EEPROM, flash memory, solid-state storage, magnetic disk storage,optical storage, and/or other computer-readable media technology.Further, in some cases, the electronic device 102 may access externalstorage, such as RAID storage systems, storage arrays, network attachedstorage, storage area networks, cloud storage, or any other medium thatcan be used to store information and that can be accessed by theprocessor 602 directly or through another computing device or network.Accordingly, the computer-readable media 604 may be computer storagemedia able to store instructions, modules, or components that may beexecuted by the processor 602. Further, when mentioned, non-transitorycomputer-readable media exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

The computer-readable media 604 may be used to store and maintain anynumber of functional components that are executable by the processor602. In some implementations, these functional components compriseinstructions or programs that are executable by the processor 602 andthat, when executed, implement operational logic for performing theactions attributed above to the electronic device 102. Functionalcomponents of the electronic device 102 stored in the computer-readablemedia 604 may include the power management service 114 and theapplications 116. In some examples, the power management service 114 maybe one or more executable modules of the operating system 112, while inother examples, some or all of the modules of the power managementservice 114 may be separate from the operating system 112. Additionalfunctional components may include the other OS modules 117 of theoperating system 112 for controlling and managing various functions ofthe electronic device 102 and for enabling basic user interactions withthe electronic device 102. For instance, the other OS modules 117 mayinclude a GPU driver 615 and a display driver 617 that are controlled insome examples herein for limiting the frame rendering rate and thedisplay refresh rate and/or display brightness, respectively.

The computer-readable media 604 may store the application data 118,application metadata 120, content items 122, the usage log 124, and thecomputational model 126. In addition, depending on the type of theelectronic device 102, the computer-readable media 604 may also storeother functional components and data, such as other modules and data618, which may include applications, programs, drivers, etc., and otherdata used or generated by the functional components. Further, theelectronic device 102 may include many other logical, programmatic, andphysical components, of which those described are merely examples thatare related to the discussion herein.

The communication interface(s) 606 may include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 106 or directly. For example,communication interface(s) 606 may enable communication through one ormore of the Internet, cable networks, cellular networks, wirelessnetworks (e.g., Wi-Fi) and wired networks, as well as close-rangecommunications such as BLUETOOTH®, and the like, as additionallyenumerated elsewhere herein.

FIG. 6 further illustrates that the electronic device 102 may includethe display 130. Depending on the type of computing device used as theelectronic device 102, the display 130 may employ any suitable displaytechnology able to present digital content thereon. In some examples,the display 130 may have a touch sensor (not shown) associated with thedisplay 130 to provide a touchscreen display configured to receive touchinputs for enabling interaction with a UI presented on the display 130.Accordingly, implementations herein are not limited to any particulardisplay technology.

The electronic device 102 may further include the GPS receiver 132 andone or more other sensors 620, such as an accelerometer, gyroscope,compass, the proximity sensor, and the like. The electronic device 102may further include one or more other I/O devices 608. The I/O devices608 may include the speakers, a microphone, one or more cameras, andvarious user controls (e.g., buttons, a joystick, a keyboard, a keypad,etc.), a haptic output device, and so forth. Additionally, theelectronic device 102 may include the battery 110 and various othercomponents that are not shown, examples of which may include removablestorage, a power control unit, and so forth.

FIG. 7 illustrates select components of the one or more servicecomputing device(s) 108 that may be used to implement some functionalityof the power management service described herein. In some examples, theservice computing device 108 may be operated by a service provider thatprovides the network storage service, and may include one or moreservers or other types of computing devices that may be embodied in anynumber of ways. For instance, in the case of a server, the modules,other functional components, and data storage (e.g., storage devices140) may be implemented on a single server, a cluster of servers, aserver farm or data center, a cloud-hosted computing service, acloud-hosted storage service, and so forth, although other computerarchitectures may additionally or alternatively be used.

Further, while the figures illustrate the components and data of theservice computing device 108 as being present in a single location,these components and data may alternatively be distributed acrossdifferent computing devices and different locations in any mannerConsequently, the functions may be implemented by one or more servicecomputing devices, with the various functionality described abovedistributed in various ways across the different computing devices.Multiple service computing devices 108 may be located together orseparately, and organized, for example, as virtual servers, serverbanks, and/or server farms. The described functionality may be providedby the servers of a single entity or enterprise, or may be provided bythe servers and/or services of multiple different buyers or enterprises.

In the illustrated example, each service computing device 108 mayinclude, or may have associated therewith, one or more processors 702,one or more computer-readable media 704, and one or more communicationinterfaces 706. Each processor 702 may be a single processing unit or anumber of processing units, and may include single or multiple computingunits, or multiple processing cores. The processor(s) 702 can beimplemented as one or more microprocessors, microcomputers,microcontrollers, digital signal processors, central processing units,state machines, logic circuitries, and/or any devices that manipulatesignals based on operational instructions. For instance, theprocessor(s) 702 may be one or more hardware processors and/or logiccircuits of any suitable type specifically programmed or configured toexecute the algorithms and processes described herein. The processor(s)702 can be configured to fetch and execute computer-readableinstructions stored in the computer-readable media 704, which canprogram the processor(s) 702 to perform the functions described herein.

The computer-readable media 704 may include the storage devices 140discussed above with respect to FIG. 1 (not shown in FIG. 7). In somecases, the storage devices 140 may be at the same location as theservice computing device(s) 108, while in other examples, the storagedevices 140 may be remote from the service computing device(s) 108. Thecomputer-readable media 704 may further include volatile and nonvolatilememory and/or removable and non-removable media implemented in any typeof technology for storage of information, such as computer-readableinstructions, data structures, program modules, or other data. Suchcomputer-readable media 704 may include, but is not limited to, RAM,ROM, EEPROM, flash memory or other memory technology, optical storage,solid state storage, magnetic tape, magnetic disk storage, RAID storagesystems, storage arrays, network attached storage, storage areanetworks, cloud storage, or any other medium that can be used to storethe desired information and that can be accessed by a computing device.Depending on the configuration of the service computing device 108, thecomputer-readable media 704 may be a type of computer-readable storagemedia and/or may be a tangible non-transitory media to the extent thatwhen mentioned, non-transitory computer-readable media exclude mediasuch as energy, carrier signals, electromagnetic waves, and signals perse.

The computer-readable media 704 may be used to store any number offunctional components that are executable by the processors 702. In manyimplementations, these functional components comprise instructions orprograms that are executable by the processors 702 and that, whenexecuted, specifically configure the one or more processors 702 toperform the actions attributed above to the service computing device108. Functional components stored in the computer-readable media 704 mayinclude the service module 138. Additional functional components storedin the computer-readable media 704 may include an operating system 708for controlling and managing various functions of the service computingdevice 108.

In addition, the computer-readable media 704 may store data used forperforming the functions and services described herein. Thus, thecomputer-readable media 704 may store the usage information 142, thecomputational model 126, the training data 146, and the other user data148. The service computing device 108 may also include or maintain otherfunctional components and data, such as other modules and data 710,which may include programs, drivers, etc., and the data used orgenerated by the functional components. Further, the service computingdevice 108 may include many other logical, programmatic, and physicalcomponents, of which those described above are merely examples that arerelated to the discussion herein.

The communication interface(s) 706 may include one or more interfacesand hardware components for enabling communication with various otherdevices, such as over the network(s) 106. For example, communicationinterface(s) 706 may enable communication through one or more of theInternet, cable networks, cellular networks, wireless networks (e.g.,Wi-Fi) and wired networks, as well as short-range communications such asBLUETOOTH®, and the like, as additionally enumerated elsewhere herein.

The service computing device 108 may further be equipped with variousinput/output (I/O) devices 712. Such I/O devices 712 may include adisplay, various user interface controls (e.g., buttons, joystick,keyboard, mouse, touch screen, etc.), audio speakers, connection portsand so forth.

Various instructions, methods, and techniques described herein may beconsidered in the general context of computer-executable instructions,such as program modules stored on computer-readable media, and executedby the processor(s) herein. Generally, program modules include routines,programs, objects, components, data structures, etc., for performingparticular tasks or implementing particular abstract data types. Theseprogram modules, and the like, may be executed as native code or may bedownloaded and executed, such as in a virtual machine or otherjust-in-time compilation execution environment. Typically, thefunctionality of the program modules may be combined or distributed asdesired in various implementations. An implementation of these modulesand techniques may be stored on computer storage media or transmittedacross some form of communication media.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as example forms ofimplementing the claims.

What is claimed is:
 1. An electronic device comprising: one or moreprocessors; a display coupled to the one or more processors; and one ormore computer-readable media storing instructions executable by the oneor more processors, for programming the one or more processors to:determine a target time to which a battery charge is to last; determinea current amount of the battery charge; determine one or more useractivities likely to occur between a present time and the target time;determine an amount of the battery charge predicted to be depletedbetween the present time and the target time based on the predicted useractivities; and based at least partially on the amount of the batterycharge predicted to be depleted, apply one or more power managementrestrictions to one or more resources of the electronic device.
 2. Theelectronic device as recited in claim 1, wherein the one or more powermanagement restrictions include at least one of: restricting a number offrames per second rendered for presentation on the display; orrestricting a refresh rate of the display.
 3. The electronic device asrecited in claim 1, wherein: the one or more power managementrestrictions are applied according to a plurality of stages, wherein afirst stage includes less restrictive power management restrictions anda second stage includes more restrictive power management restrictions;and one of the first stage or the second stage is selected based atleast partially on the amount of the battery charge remaining and theuser activities determined to be likely to occur before the target time.4. The electronic device as recited in claim 1, further comprising atleast one of: a plurality of application-specific power managementprofiles stored in the computer-readable media, eachapplication-specific power management profile indicating the one or morepower management restrictions to apply to the one or more resources foran individual application of a plurality of applications installed onthe electronic device; or a plurality of application category powermanagement profiles stored in the computer-readable media, eachapplication category power management profile indicating the one or morepower management restrictions to apply to the one or more resources fora category of application installed on the electronic device.
 5. Theelectronic device as recited in claim 1, wherein the one or moreprocessors are further programmed to determine the one or more useractivities likely to occur between the present time and the target timebased at least partially on a usage log stored in the one or morecomputer-readable media, wherein the usage log includes at least one of:an identifier of a respective application or feature used; a time andday of usage the respective application or feature; a geographiclocation of the usage; a change in battery charge amount determinedbased on the usage; or a power management mode in effect during theusage.
 6. The electronic device as recited in claim 5, wherein the oneor more processors are further programmed to: send, to a computingdevice over a network, at least a portion of information included in theusage log; and receive, from the computing device, a computational modelgenerated based at least partially on the portion of information sentover the network.
 7. The electronic device as recited in claim 6,wherein the one or more processors are further programmed to determineat least one of the target time or the predicted user activities basedat least partially on at least one of: the usage log; the computationalmodel; or a received user input.
 8. A method comprising: determining, bya processor of an electronic device, a target time to which a batterycharge is to last; determining a current amount of the battery chargeremaining; determining one or more user activities likely to occurbetween a present time and the target time; and based at least partiallyon the amount of the battery charge remaining and the one or more useractivities determined to be likely to occur before the target time,applying one or more power management restrictions to one or moreresources of the electronic device.
 9. The method as recited in claim 8,wherein applying one or more power management restrictions furthercomprises at least one of: restricting a number of frames per secondrendered for presentation on a display associated with the electronicdevice; or restricting a refresh rate of the display.
 10. The method asrecited in claim 8, further comprising: applying the one or more powermanagement restrictions according to one of a plurality of stages,wherein a first stage includes less restrictive power managementrestrictions and a second stage includes more restrictive powermanagement restrictions; and selecting one of the first stage or thesecond stage based at least partially on the amount of the batterycharge remaining and the user activities determined to be likely tooccur before the target time.
 11. The method as recited in claim 8,further comprising applying the one or more power managementrestrictions according to at least one of an application-specific powermanagement profile or an application category power management profile,the application-specific power management profile indicating the one ormore power management restrictions to apply to the one or more resourcesfor an individual application of a plurality of applications installedon the electronic device, and the application category power managementprofile indicating the one or more power management restrictions toapply to the one or more resources for a category of applicationinstalled on the electronic device.
 12. The method as recited in claim8, further comprising storing, in a usage log, a record of anapplication and/or feature used on the electronic device, wherein theusage log includes at least one of: an identifier of a respectiveapplication or feature used; a time and day of usage the respectiveapplication or feature; a geographic location of the usage; a change inbattery charge amount determined based on the usage; or a powermanagement mode in effect during the usage.
 13. The method as recited inclaim 12, further comprising: sending, to a computing device over anetwork, at least a portion of information included in the usage log;and receiving, from the computing device, a computational modelgenerated based at least partially on the portion of information sentover the network.
 14. The method as recited in claim 13, furthercomprising determining at least one of the target time or the predicteduser activities based at least partially on at least one of: the usagelog; the computational model; or a received user input.
 15. One or morenon-transitory computer-readable media maintaining instructions that,when executed by one or more processors of an electronic device, programthe one or more processors to: determine a target time to which abattery charge is to last; determine a current amount of the batterycharge remaining; determine one or more user activities likely to occurbetween a present time and the target time; and based at least partiallyon the amount of the battery charge remaining and the one or more useractivities determined to be likely to occur before the target time,apply one or more power management restrictions to one or more resourcesof the electronic device.
 16. The one or more non-transitorycomputer-readable media as recited in claim 15, wherein the one or moreprocessors are further programmed to: determine an amount of the batterycharge predicted to be depleted between the present time and the targettime based on the predicted user activities; and determine the one ormore power management restrictions to apply based at least partially onthe an amount of the battery charge predicted to be depleted before thetarget time.
 17. The one or more non-transitory computer-readable mediaas recited in claim 15, wherein the one or more processors are furtherprogrammed to apply the one or more power management restrictions by atleast one of: restricting a number of frames per second rendered forpresentation on a display associated with the electronic device; orrestricting a refresh rate of the display.
 18. The one or morenon-transitory computer-readable media as recited in claim 15, whereinthe one or more processors are further programmed to: apply the one ormore power management restrictions according to one of a plurality ofstages, wherein a first stage includes less restrictive power managementrestrictions and a second stage includes more restrictive powermanagement restrictions; and apply the one or more power managementrestrictions according to at least one of an application-specific powermanagement profile or an application category power management profile,the application-specific power management profile indicating the one ormore power management restrictions to apply to the one or more resourcesfor an individual application of a plurality of applications installedon the electronic device, and the application category power managementprofile indicating the one or more power management restrictions toapply to the one or more resources for a category of applicationinstalled on the electronic device.
 19. The one or more non-transitorycomputer-readable media as recited in claim 15, wherein the one or moreprocessors are further programmed to store, in a usage log, a record ofan application and/or feature used on the electronic device, wherein theusage log includes at least one of: an identifier of a respectiveapplication or feature used; a time and day of usage the respectiveapplication or feature; a geographic location of the usage; a change inbattery charge amount determined based on the usage; or a powermanagement mode in effect during the usage.
 20. The one or morenon-transitory computer-readable media as recited in claim 19, whereinthe one or more processors are further programmed to: send, to acomputing device over a network, at least a portion of informationincluded in the usage log; receive, from the computing device, acomputational model generated based at least partially on the portion ofinformation sent over the network; and determine at least one of thetarget time or the predicted user activities based at least partially onthe computational model.